Skip to content

Do not reparse the full (already parsed) IOP after new segments arrive - #708

Open
martonmiklos wants to merge 2 commits into
mainfrom
martonmiklos/do_not_reparse_whole_iop_after_segment_reception
Open

Do not reparse the full (already parsed) IOP after new segments arrive#708
martonmiklos wants to merge 2 commits into
mainfrom
martonmiklos/do_not_reparse_whole_iop_after_segment_reception

Conversation

@martonmiklos

Copy link
Copy Markdown
Contributor

Describe your changes

In the case an IOP segment is being transferred the whole pool is being reparsed.

This means in the case if some object properties (like object hide/show state) are being set by commands after the reparsing these changes will be lost. This goes against the what the standard says about the visibility effect:

kép

Fixes #Open-Agriculture/AgIsoVirtualTerminal/201

How has this been tested?

Built AgIsoVT with this stack version and checked a side effect caused by the reparsing, which is gone after this fix.

@martonmiklos
martonmiklos force-pushed the martonmiklos/do_not_reparse_whole_iop_after_segment_reception branch 3 times, most recently from 0e0d97c to 2cda851 Compare August 18, 2026 07:53
@sujandumaru

Copy link
Copy Markdown
Member

Is it possible to add a test for this?

@martonmiklos martonmiklos changed the title Do not reparse the full already parsed IOP after new segments arrive Do not reparse the full (already parsed) IOP after new segments arrive Sep 4, 2026
@martonmiklos
martonmiklos force-pushed the martonmiklos/do_not_reparse_whole_iop_after_segment_reception branch 2 times, most recently from 2cb879b to a291862 Compare September 4, 2026 20:08
@martonmiklos
martonmiklos force-pushed the martonmiklos/do_not_reparse_whole_iop_after_segment_reception branch from a291862 to 822a31c Compare September 4, 2026 20:09
@martonmiklos

Copy link
Copy Markdown
Contributor Author

Is it possible to add a test for this?

I have added an unit test to cover this feature.

@sonarqubecloud

sonarqubecloud Bot commented Sep 4, 2026

Copy link
Copy Markdown

@sujandumaru sujandumaru left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be better if we can add the "explicit" on the constructor with one argument as suggested by SonarCloud.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants